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

fix: Drop :8080 port suffix from S3 how-to guides #264

Merged
merged 1 commit into from
Jan 12, 2024

Conversation

fghaas
Copy link
Contributor

@fghaas fghaas commented Dec 18, 2023

Now that all our object storage services are listening on the regular HTTPS port (443), we no longer need to list the :8080 suffix in our how-to guides for S3.

We still do need to keep the suffix in the how-to guides for Swift, since our object-storage endpoints in our service catalogs still do contain the :8080 suffix.

Copy link
Contributor

@colder-is-better colder-is-better left a comment

Choose a reason for hiding this comment

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

LGTM!

@pejotes
Copy link
Contributor

pejotes commented Dec 19, 2023

This looks good to me as well.

@fghaas
Copy link
Contributor Author

fghaas commented Dec 19, 2023

Split the one commit into two since we're having to handle this change separately for the S3 and Swift APIs. Tracking the Swift-related update in #265.

@fghaas fghaas changed the title fix: Drop :8080 port suffix from object storage how-to guides fix: Drop :8080 port suffix from S3 how-to guides Dec 19, 2023
Now that all our object storage services are listening on the regular
HTTPS port (443), we no longer need to list the :8080 suffix in our
how-to guides for S3.

We still do need to keep the suffix in the how-to guides for Swift,
since our object-storage endpoints in our service catalogs still do
contain the :8080 suffix.
@fghaas
Copy link
Contributor Author

fghaas commented Jan 12, 2024

@colder-is-better This will need a re-review please, due to having been rebased on current main. Thanks!

@fghaas fghaas merged commit 5d05a14 into citynetwork:main Jan 12, 2024
3 checks passed
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.

4 participants