Skip to content
This repository has been archived by the owner on Nov 2, 2024. It is now read-only.

feat: Implement COB artifact configurations #1056

Closed

Conversation

minherz
Copy link
Contributor

@minherz minherz commented Oct 27, 2023

[TBD]

@minherz minherz added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Oct 27, 2023
@minherz minherz self-assigned this Oct 27, 2023
fix broken links in markdown.
refactor variable initializations and OB kustomization path.
add placeholder for OB configuration of COB artifacts
bring the COB version as argument to Terraform configuration instead of
reading it from external file.
rename filepath_manifest to be manifest_filepath
make it required variable in the microservice_demo module
make it configuration_filepath
allow providing custom set of variables that can be used
to provision COS artifacts based on the configurations.
add uptime check configuration schema file.
add uptime check configuration validation to CI workflow.
add uptime check configuration for OB demo app.
add uptime check configuration for test configuration to be run in CI.
modifle CLI to provide configuration parameter when running terraform.
add uptimecheck provisioning to the cloud-ops terraform module.
modify main terraform configuration (main.tf) to support modified
cloud-ops module.
refactor input variable names from filepath_* to *_filepath.
remove redundant network.tf file.
make timeout as formatted string
refactor metric schema to use underscore instead dash in field names
implement log-based metrics config for OB
modify TF files to support provisioning metrics from config file
alter notification channels schema (in alerts) to simplify provisioning.
adjust test configuration and add OB configuration.
update TF to support notification channels provisioning from config.
adding most recent changes to save work
@minherz minherz force-pushed the minherz/use-config-in-cloud-ops-module branch from d253416 to ecc2319 Compare November 25, 2023 20:09
@minherz minherz closed this Sep 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
do not merge Indicates a pull request not ready for merge, due to either quality or timing.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant