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

Inventory-next Datapusher configuration updated #2037

Closed
1 task done
jbrown-xentity opened this issue Aug 14, 2020 · 1 comment
Closed
1 task done

Inventory-next Datapusher configuration updated #2037

jbrown-xentity opened this issue Aug 14, 2020 · 1 comment
Assignees
Labels
component/inventory Inventory playbooks/roles

Comments

@jbrown-xentity
Copy link
Contributor

jbrown-xentity commented Aug 14, 2020

User Story

As a data.gov developer, I want inventory-next to deploy datapusher using the latest configuration so that upstream repositories and best practices are being used as much as possible.

Acceptance Criteria

  • GIVEN I ssh onto inventory-next
    WHEN I view the supervisorctl status output
    THEN datapusher is running

Background

Related to #1678. Blocks #1675

Security Considerations (required)

None

Sketch

  • Will need to possibly create separate role to deploy using gunicorn and add tests.
  • Should be able to implement upstream version; if not straightforward then create separate ticket and implement GSA current version
  • Only implement this latest version for inventory-next, may need an inventory-next variable set up to implement.
@jbrown-xentity
Copy link
Contributor Author

This PR looks to be working, but has not been fully tested and requires testing on staging. Should test classic configuration on staging (only accessible currently working version) before pushing to production.

I no longer think this is related to/blocking #2038, should be able to move forward with that ticket without merging this.

@mogul mogul added this to the Sprint 20200903 milestone Sep 3, 2020
@mogul mogul closed this as completed Sep 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/inventory Inventory playbooks/roles
Projects
None yet
Development

No branches or pull requests

2 participants