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

feat: add Elasticsearch DA #21

Open
wants to merge 7 commits into
base: dev-elasticsearch
Choose a base branch
from
Open

feat: add Elasticsearch DA #21

wants to merge 7 commits into from

Conversation

akocbek
Copy link
Contributor

@akocbek akocbek commented Jul 10, 2024

Description

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@akocbek akocbek changed the base branch from main to dev-elasticsearch July 11, 2024 09:23
Copy link
Member

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

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

left some more suggestions. I think you need to add the outputs to the ibm_catalog.json in order to mark some of them as sensitive and to add a description to them.

],
"outputs": [
{
"name": "es_hostname",
Copy link
Member

Choose a reason for hiding this comment

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

es_hostname -> elasticsearch_hostname

"value": "ref:./members/7 - Databases for Elasticsearch/outputs/hostname"
},
{
"name": "es_port",
Copy link
Member

Choose a reason for hiding this comment

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

es_port -> elasticsearch_port

"value": "ref:./members/7 - Databases for Elasticsearch/outputs/port"
},
{
"name": "es_certificate_base64",
Copy link
Member

Choose a reason for hiding this comment

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

es_certificate_base64 -> elasticsearch_certificate_base64

"value": "ref:./members/7 - Databases for Elasticsearch/outputs/certificate_base64"
},
{
"name": "es_service_credentials_json",
Copy link
Member

Choose a reason for hiding this comment

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

es_service_credentials_json -> elasticsearch_service_credentials_json

@ocofaigh
Copy link
Member

Do we need to explicitly pass a value for service_credential_names in order to generate service credentials? Otherwise I don't think credentials will be created? Can you check?

@ocofaigh
Copy link
Member

@akocbek perhaps include the changes from #20 in this PR too?

}
}
],
"name": "7 - Databases for Elasticsearch",
Copy link
Member

Choose a reason for hiding this comment

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

Should this be renamed "3b - Databases for Elasticsearch" since it has a dependency on 1 - Account Infrastructure Base and 2a - Security Service - Key Management only (and then rename 3a - Security Service - Observability)?

Copy link
Member

Choose a reason for hiding this comment

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

going with this for now - will revisit later

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