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

CF table updates - default to CF app name to match GSFC apps, disable polling by default #186

Closed
skliper opened this issue Feb 1, 2022 · 0 comments · Fixed by #187
Closed

Comments

@skliper
Copy link
Contributor

skliper commented Feb 1, 2022

Checklist (Please check before submitting)

  • [ x] I reviewed the Contributing Guide.
  • [ x] I reviewed the CF README.md file to see if the feature is in the major future work.
  • [ x] I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
Current table name follows lab app pattern w/ *_APP, but GSFC apps don't have the _APP. Polling directory enabled by default means the warnings/errors about no polling directory existing will show up unless created by the user. Prefer default behavior to not see these.

Describe the solution you'd like
Change CF_APP to CF in table, set polling to disabled

Describe alternatives you've considered
Users can override, so not a big deal but nice to stay consistent with apps. If we want to add *_APP everywhere probably makes more sense as a bulk update. Note may run into name length issues on other apps by using up the extra 4 chars.

Additional context
None

Requester Info
Jacob Hageman - NASA/GSFC

@skliper skliper added this to the Draco milestone Feb 1, 2022
skliper added a commit to skliper/CF that referenced this issue Feb 1, 2022
astrogeco added a commit that referenced this issue Feb 3, 2022
Fix #186, CF table name and default polling disabled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant