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

store initial configuration of the service during service deployment #1774

Closed
5 tasks done
swaroopar opened this issue Jul 2, 2024 · 1 comment · Fixed by #1784
Closed
5 tasks done

store initial configuration of the service during service deployment #1774

swaroopar opened this issue Jul 2, 2024 · 1 comment · Fixed by #1784
Assignees
Labels
Accepted Issues that have been accepted and planned enhancement New feature or request

Comments

@swaroopar
Copy link
Contributor

swaroopar commented Jul 2, 2024

As part of service configuration update, we must start with storing initial service configuration properties during the service deployment.

  • Add new table SERVICE_CONFIGURATION with foreign Key as the ID of the DEPLOY_SERVICE table. and CONFIGURATION column
  • CONFIGURATION column stored configuration as JSON.
  • Add created and updated time columns
  • Extract initial configuration as below -
    1. JSON Key is name of ServiceConfigurationParameter
    2. Value is the initialValue of ServiceConfigurationParameter
    3. If the same name is present in the flavor properties, then that value from the deployed flavor must be used as the initial value.
  • Use kafka service properties from bitnami kafka docker image and update the service template
    https://github.com/bitnami/containers/tree/main/bitnami/kafka#111-debian-9-r205-220-debian-9-r40-111-ol-7-r286-and-220-ol-7-r53
    To start with, we can only provide the following configuration parameters in the template - KAFKA_CFG_MESSAGE_MAX_BYTES, KAFKA_CFG_LOG_DIRS, KAFKA_CFG_NUM_IO_THREADS, KAFKA_LOG_FLUSH_INTERVAL_MESSAGES, KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR
@swaroopar swaroopar added this to the Sprint 072024_1 milestone Jul 2, 2024
@swaroopar swaroopar added enhancement New feature or request Accepted Issues that have been accepted and planned labels Jul 2, 2024
@WangLiNaruto
Copy link
Contributor

let me do it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Issues that have been accepted and planned enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants