CASMCMS-8651: Update two example strings in API spec to refer to S3 instead of ARS #60
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mharding-hpe
force-pushed
the
CASMCMS-8651
branch
from
a666b4d to
d92c2b8
Compare
mharding-hpe
force-pushed
the
CASMCMS-8651
branch
from
d92c2b8 to
5231e84
Compare
mjendrysik-hpe
approved these changes
May 30, 2023
1 task
shunr-hpe
approved these changes
May 31, 2023
jnowicki-hpe
approved these changes
May 31, 2023
nieuwsma
approved these changes
Jun 1, 2023
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary and Scope
I noticed that the BSS API spec still refers to ARS in a couple of example strings. This PR updates those to be S3 links, reflecting what is now seen on CSM systems. Not a huge deal, but the ARS reference could cause confusion to someone who noticed it.
DOES THIS CHANGE INVOLVE ANY SCHEME CHANGES? N
REMINDER: HAVE YOU INCREMENTED VERSION NUMBERS? Y
REMINDER 2: HAVE YOU UPDATED THE COPYRIGHT PER hpe GUIDELINES: (C) Copyright 2014-2021 Hewlett Packard Enterprise Development LP ? N/A
Issues and Related PRs
Testing
No testing -- only contents of two example strings is changed.
Risks and Mitigations
Minimal risk.