Closed gregbunce closed 3 years ago
blocked by #103
If the schema is the same or a superset of what we are serving we do not need to deprecate or brownout. We can wire up forklift and be on our way.
meeting update
still blocked by #103
@steveoh can we get a tweet out (or maybe we did already) saying we're deprecating this LRS layer in 30 days on March 5th (or if we tweet on Monday then March 8th)?
we're deprecating this LRS layer: https://opendata.gis.utah.gov/datasets/utah-udot-routes-lrs
it's been replaced by this ALRS (Advanced) layer: https://opendata.gis.utah.gov/datasets/uplan::udot-routes-alrs
More info on the newest layer can be found here: https://gis.utah.gov/data/transportation/roads-system/#HighwayLinearReferencingSystemRoutes
check | status |
---|---|
@gregbunce has completed 2 out of 3 tasks | :no_entry: |
@steveoh has completed 2 out of 3 tasks | :no_entry: |
stdavis has completed 1 out of 1 tasks | :+1: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | :no_entry: Did not find Transportation.UDOTRoutesLRS in the worksheet |
a brownout on this layer is now in effect. if all goes as expected, this layer will be removed from the sgid Monday, March 8, 2021.
this layer has been removed from AGOL and has been backed up in the AGRC google drive in the deprecated directory.
i just realized that i did a brownout only on the AGOL item, but forgot to brownout the Internal SGID layer. I just removed the "Internal" user privileges from this layer. I'll let that sit for a day and then delete it from the db tomorrow if there were no internal dependencies/issues.
@steveoh, @jacobdadams - am i safe to delete the AGOLItems record for this layer (at least from your standpoints)?
That will remove it from the open sgid. Jake will have to speak to the auditor parts. Especially the brown out situation. Auditor might un brown your out if that record still exists?
For the record, Auditor will run it's fixes on any row in the metatable with a valid AGOL_ITEM_ID value (it tries parsing the GUID, and if it can't it ignores the row). If you want Auditor to ignore a row, replace the id with text like Removed from AGOL
.
Also, Auditor will share any item it finds a proper group for (which currently comes from the category portion of SGID.GROUPNAME.TableName
) to both the group and everyone else. So, if you unshare something that is being picked up by Auditor, Auditor will reshare it.
@steveoh looks like we can close this out once the SGID.META.ChangeDetection process/table is satisfied.
well i think i deleted the advanced change detection row as well but that will resolve itself.
Summary
This SGID LRS layer was replaced by UDOT's newer Advanced LRS (ALRS) hosted feature service described in porter issue 103. Please migrate all existing maps and app at your earliest convenience. A notification of this change was also sent via Twitter
AGRC will perform a brownout on this layer on March 5th, 2021 with a complete deprecation on March 8th, 2021.
Triage
Remove data from the following areas
Update information in the following areas
SGID.META.AGOLItems
(@gregbunce on '03/08/2021' )SGID.META.ChangeDetection
(assigned to @steveoh )Notification