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

Display data catalogue version on the status page #355

Closed
3 tasks done
Tracked by #482
lkmorlan opened this issue Feb 7, 2024 · 5 comments
Closed
3 tasks done
Tracked by #482

Display data catalogue version on the status page #355

lkmorlan opened this issue Feb 7, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request Sprint 14 February 22 - March 13 Sprint 15 March 14 - April 3 Sprint 16 April 4- April 24 Sprint 17 April 25 - May 16 Sprint 18 May 17 - May 30

Comments

@lkmorlan
Copy link
Collaborator

lkmorlan commented Feb 7, 2024

OP timer

https://openplus.monday.com/boards/4092908516/pulses/6020732089


User story

As anyone who can see the status report

I want to see the data catalogue version number

So that I know what version I am on.

Proposed solution

Write a custom hook_requirements() implementation

Estimated level of effort

  • Less than 1 day

Definition of done (DoD)

  • Version number appears as an item in the status report

Testing

Automated functional tests

  • I have written functional tests for this feature
  • I have run the functional tests and they pass
@lkmorlan lkmorlan added the enhancement New feature or request label Feb 7, 2024
@NicoledeGreef NicoledeGreef added this to the Administration milestone Feb 8, 2024
@NicoledeGreef NicoledeGreef added the Sprint 14 February 22 - March 13 label Feb 16, 2024
@lkmorlan
Copy link
Collaborator Author

It turns out the composer_deploy is not suitable for this because the bc_dc module does not come in via Composer. We can get the information needed using Git.

@lkmorlan
Copy link
Collaborator Author

The current approach does not work in our environment. I have discussed another solution with @sylus .

@lkmorlan
Copy link
Collaborator Author

The code now gets the version from the info file of bc_dc. @sylus will adjust the deployment script so that it adds a version key to this file.

@lkmorlan lkmorlan assigned sylus and unassigned lkmorlan Mar 14, 2024
@NicoledeGreef NicoledeGreef added the Sprint 15 March 14 - April 3 label Mar 15, 2024
@NicoledeGreef NicoledeGreef added the Sprint 16 April 4- April 24 label Apr 4, 2024
@NicoledeGreef NicoledeGreef added the Sprint 17 April 25 - May 16 label Apr 25, 2024
@sylus
Copy link
Collaborator

sylus commented May 6, 2024

@CraigClark I can get this done Monday night it just takes some finagling with yq.

@sylus
Copy link
Collaborator

sylus commented May 23, 2024

I believe I have addressed this now by writing to the bc_dc.info.yml file during the dev build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Sprint 14 February 22 - March 13 Sprint 15 March 14 - April 3 Sprint 16 April 4- April 24 Sprint 17 April 25 - May 16 Sprint 18 May 17 - May 30
Projects
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants