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

[Chore]: Update the URL fragment for API keys #658

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

shasts
Copy link
Member

@shasts shasts commented Jul 11, 2024

Description

The API keys URL fragment was updated. But the docs here and a couple of other lingering pieces were not. This PR updates the reference in this repo to reflect the latest URL.

Corresponding cloud PR. https://github.com/elastic/cloud/pull/129503

Related Issues

Motivation and Context

How Has This Been Tested?

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (improves code quality but has no user-facing effect)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation

Readiness Checklist

  • My code follows the code style of this project
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed

@shasts shasts self-assigned this Jul 11, 2024
@shasts shasts requested review from alaudazzi and a team as code owners July 11, 2024 08:50
Copy link
Contributor

@dimuon dimuon left a comment

Choose a reason for hiding this comment

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

LGTM

@shasts shasts merged commit 92d35ea into elastic:master Jul 11, 2024
3 checks passed
@shasts shasts deleted the fix/keys-update-docs branch July 11, 2024 09:19
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.

2 participants