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

Update CubeJS Configuration and Deploy New Image for CA Queries #30383

Open
victoralfaro-dotcms opened this issue Oct 17, 2024 · 0 comments
Open

Comments

@victoralfaro-dotcms
Copy link
Contributor

victoralfaro-dotcms commented Oct 17, 2024

User Story

As a dev-ops engineer, I want to change the CubeJS Events.js configuration file to include the latest queries for CA. Besides the pasting of the actual changes, we will need to build a new image to be used in both dev and prod environments for CubeJS pods. The produced hash will be used in the helm configuration files to be deployed with the latest changes.

Acceptance Criteria

  • CubeJS Events.js configuration file is updated with the latest CA queries.
  • New CubeJS image is built and tagged with the correct hash.
  • Hash is updated in the helm configuration files.
  • Deployment is successful in both dev and prod environments.

dotCMS Version

master

Proposed Objective

Integrations

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

Assumptions & Initiation Needs

  • Access to the latest CA query configurations.
  • Permissions to build and push CubeJS images.

Quality Assurance Notes & Workarounds

  • Ensure that the new queries return expected data in dev and prod environments.
  • Test the deployment in dev before moving to prod.

Sub-Tasks & Estimates

  1. Update CubeJS Events.js with new CA queries (2 hours).
  2. Build new CubeJS image and tag hash (1 hour).
  3. Update helm configuration files with new image hash (30 minutes).
  4. Test deployment in dev environment (1 hour).
  5. Deploy to prod environment (1 hour).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant