Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ADR and appnote specifying get_urls label format #72

Merged
merged 11 commits into from
Aug 2, 2024

Conversation

j616
Copy link
Contributor

@j616 j616 commented Jul 5, 2024

Details

Add ADR and appnote specifying get_urls label format

Pivotal Story (if relevant)

Story URL: https://www.pivotaltracker.com/story/show/187593257

Related PRs

Where appropriate. Indicate order to be merged.

Submitter PR Checks

(tick as appropriate)

  • PR completes task/fixes bug
  • API version has been incremented if necessary
  • ADR status has been updated, and ADR implementation has been recorded
  • Documentation updated (README, etc.)
  • PR added to Pivotal story (if relevant)
  • Follow-up stories added to Pivotal

Reviewer PR Checks

(tick as appropriate)

  • PR completes task/fixes bug
  • Design makes sense, and fits with our current code base
  • Code is easy to follow
  • PR size is sensible
  • Commit history is sensible and tidy

Info on PRs

The checks above are guidelines. They don't all have to be ticked, but they should all have been considered.

@j616 j616 marked this pull request as ready for review July 5, 2024 13:28
@j616 j616 requested a review from a team as a code owner July 5, 2024 13:28
@j616 j616 force-pushed the jamessa-getUrlLabels branch from 03c07a2 to 36aaecd Compare July 9, 2024 08:34
@samdbmg samdbmg self-assigned this Jul 22, 2024
Copy link
Member

@samdbmg samdbmg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - couple of nits inlined

docs/adr/0021-storage-label-format.md Outdated Show resolved Hide resolved
docs/adr/0021-storage-label-format.md Outdated Show resolved Hide resolved
docs/adr/0021-storage-label-format.md Outdated Show resolved Hide resolved
docs/adr/0021-storage-label-format.md Outdated Show resolved Hide resolved
docs/appnotes/0009-storage-label-format.md Outdated Show resolved Hide resolved
docs/appnotes/0009-storage-label-format.md Outdated Show resolved Hide resolved
@j616 j616 force-pushed the jamessa-getUrlLabels branch from 56878ba to c20602a Compare July 22, 2024 14:02
```

The parameters `provider`, `region`, `availabilityZone`, and `storeType` should use the machine readable values as provided by the cloud/storage vendor.
The intention of this approach is to allow consistent values to be used without enumerating common/possible values in TAMS.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sadly I think a level of enumeration is going to be necessary somewhere for consistency. For example is AWS listed as 'amazon' or 'aws'? Regions is probably the simplest for public clouds as you can take their naming convention, eg 'eu-west-1', however the same will be necessary at the storage product level for example to describe S3 Express One Zone in a common way.

These probably will ultimately need to end up in an app note somewhere similar to the tags list, so not part of the API spec or validation

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm. Is there no consistency in the likes of ARN's for aws? I'd expected inconsistency in documentation, but hoped for consistency in configuration.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies, I missed the line directly above stating where the values should come from. While the AWS ARN structure is well defined there are some oddities that stand out like s3 buckets not having the region defined. Similarly while the majority of services define the AZ in the format eu-west-1a, I have seen some exceptions to this. Ultimately it might be worth either pointing to where the enumerations come from, or alternatively giving some examples for a few of the most common storage platforms.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've expanded explanations and added examples in c46f8c3

@j616 j616 requested a review from samdbmg July 29, 2024 11:20
Copy link
Member

@samdbmg samdbmg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

docs/appnotes/0009-storage-label-format.md Outdated Show resolved Hide resolved
@j616 j616 merged commit 937e4b7 into main Aug 2, 2024
5 checks passed
@j616 j616 deleted the jamessa-getUrlLabels branch August 2, 2024 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants