Skip to content

Simplifying naming conventions in inventory files by removing the "ubi" suffix. #58

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

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

nammn
Copy link
Collaborator

@nammn nammn commented Apr 29, 2025

Summary

Simplifying naming conventions in inventory files by removing the "ubi" suffix.

Inventory File Simplifications:

  • Standardized naming conventions in agent.yaml, daily.yaml, database.yaml, init_appdb.yaml, and init_database.yaml by removing the "ubi" suffix from task and template names. This change simplifies the configuration and aligns with other naming practices. [1] [2] [3] [4] [5] [6]
  • Updated file paths in Dockerfile references to remove unnecessary subdirectories (e.g., ubi), streamlining the directory structure. [1] [2] [3]

Proof of Work

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you checked for release_note changes?

Reminder (Please remove this when merging)

  • Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
  • Our Short Guide for PRs: Link
  • Remember the following Communication Standards - use comment prefixes for clarity:
    • blocking: Must be addressed before approval.
    • follow-up: Can be addressed in a later PR or ticket.
    • q: Clarifying question.
    • nit: Non-blocking suggestions.
    • note: Side-note, non-actionable. Example: Praise
    • --> no prefix is considered a question

@nammn nammn changed the title Remove ubi Simplifying naming conventions in inventory files by removing the "ubi" suffix. Apr 29, 2025
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.

1 participant