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

Use HTTPS for AWS API Documentation links in javadocs #2311

Closed
wants to merge 2 commits into from
Closed

Use HTTPS for AWS API Documentation links in javadocs #2311

wants to merge 2 commits into from

Conversation

Carey-AWS
Copy link
Contributor

Description

The URLs in the javadocs that go to the various service API docs currently use HTTP; changing to use HTTPS.

Motivation and Context

Best practice, resolves internal ticket

Testing

mvn install completed without errors. All codegen tests run successfully.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed
  • A short description of the change has been added to the CHANGELOG
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

@Carey-AWS Carey-AWS marked this pull request as draft March 5, 2021 23:48
@Carey-AWS Carey-AWS closed this Mar 8, 2021
aws-sdk-java-automation added a commit that referenced this pull request Dec 30, 2022
…cc8d3dd5a

Pull request: release <- staging/b1084206-022c-4927-af2f-1a6cc8d3dd5a
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.

None yet

1 participant