Actions
Feature #22269
closed
Update Salt installer to use new URLs, keys
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Story points:
-
Release:
Release relationship:
Auto
Description
https://saltproject.io/blog/salt-project-package-repo-migration-and-guidance/
At the very least, tools/salt-install/provision.sh gets the old key and sets up the old apt repository URL. We will need to update that. There may be more. Go through the guide and check against the Salt installer to check for other things that need updating.
Updated by Brett Smith 22 days ago
- Status changed from New to In Progress
22269-salt-urls @ e56b0715f308bb3259ce5e9c458f351d37592027 - test-provision: #1025
- All agreed upon points are implemented / addressed.
- After this,
git grep -Fe saltproject.io -e saltstack.com(the latter seems to be an older alias for the former) returns only one documentation link and one bootstrap script download. According to the published advice, both these have moved to GitHub pages without a change in URL. So those should be fine, and we should be good everywhere else.
- After this,
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- None
- Code is tested and passing, both automated and manual, what manual testing was done is described
- Just test-provision above
- Documentation has been updated.
- N/A, no functional change
- Behaves appropriately at the intended scale (describe intended scale).
- N/A, no functional change
- Considered backwards and forwards compatibility issues between client and server.
- Change required by upstream changes
- Follows our coding standards and GUI style guidelines.
- N/A, no shell style guide
Updated by Peter Amstutz 21 days ago
Brett Smith wrote in #note-1:
22269-salt-urls @ e56b0715f308bb3259ce5e9c458f351d37592027 - test-provision: #1025
- All agreed upon points are implemented / addressed.
- After this,
git grep -Fe saltproject.io -e saltstack.com(the latter seems to be an older alias for the former) returns only one documentation link and one bootstrap script download. According to the published advice, both these have moved to GitHub pages without a change in URL. So those should be fine, and we should be good everywhere else.- Anything not implemented (discovered or discussed during work) has a follow-up story.
- None
- Code is tested and passing, both automated and manual, what manual testing was done is described
- Just test-provision above
- Documentation has been updated.
- N/A, no functional change
- Behaves appropriately at the intended scale (describe intended scale).
- N/A, no functional change
- Considered backwards and forwards compatibility issues between client and server.
- Change required by upstream changes
- Follows our coding standards and GUI style guidelines.
- N/A, no shell style guide
This LGTM
Updated by Brett Smith 21 days ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|abef901461a49441da2d91f6006f179e1009cbdd.
Actions