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

Pulling feat/modware-feature-annotation into develop #144

Open
wants to merge 11 commits into
base: develop
Choose a base branch
from

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Jan 30, 2025

  • modware-annotation-feature project created. Initialized the experiments stack.
  • containerArgs function updated to use Backend.Config.Command instead of hard-coded value
  • BackendConfig struct updated. Added Command field
  • modware-* project configs updated. Added command config entry

…main.go file for annotation feature

The changes include adding Pulumi configuration files for the feature-annotation project, which includes defining the application properties such as appName, image details, log level, and port. Additionally, the main.go file is added to define the main function for running the Pulumi program related to the annotation feature.

issue #143
…fying custom startup command

The Command field is added to the BackendConfig struct to allow specifying a custom startup command for the backend service. This enhancement provides flexibility in configuring the behavior of the backend service at startup by allowing different commands to be executed based on the provided configuration.

issue #143
…y to 'feature-annotation' for consistency

The value of the 'appName' property in the Pulumi configuration file has been updated to 'feature-annotation' to ensure consistency with the naming convention used for this specific feature.

issue #143
…on to modware-annotation-feature

The config key modware-annotation has been corrected to modware-annotation-feature to accurately reflect the project being configured.

issue #143
…y to 'annotation-feature' for consistency

The value of the 'appName' property in the Pulumi experiments configuration file has been updated to 'annotation-feature' for consistency with the actual feature name.

issue #143
…tart-feature-server command

The new command field is added to the Pulumi configuration file to specify the command that should be executed to start the feature server. This change allows for more flexibility and customization in managing the feature server within the Pulumi infrastructure.

issue #143
…umi experiment files

The 'command: start-server' has been added to all Pulumi experiment files for modware-annotation, modware-content, modware-order, and modware-stock. This change allows for consistency and ensures that the server starts correctly when deploying these services.

issue #143
…odware-annotation-feature'

The project name has been updated to 'modware-annotation-feature' to better reflect the purpose or feature of the project. This change ensures clarity and consistency in project naming conventions.

Resolves #143
@ktun95 ktun95 linked an issue Jan 30, 2025 that may be closed by this pull request
The changes were made to remove unnecessary whitespace in the Command field to maintain consistent code style and improve readability.

issue #143
a unique encryptedKey was generated for the modware-annotation-feature
project instead of duplicating the one from modware-annotation
…ryption

The encryptedkey field has been added to the Pulumi.experiments.yaml file to store an encrypted key for secrets encryption using GCP KMS. This enhances security by ensuring that sensitive information is stored securely and can only be accessed by authorized users.
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.

modware-feature
1 participant