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

feat: format (pretty-print) STAC files TDE-759 #172

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

Conversation

paulfouquet
Copy link
Collaborator

@paulfouquet paulfouquet commented Sep 12, 2023

Description

Add a WorkflowTemplate to format files that calls linz/argo-tasks pretty-print command. This template is used in imagery-standardising workflow.

Intention

Some of the STAC files (Item) are not pretty printed. Having a WorkflowTemplate allows to format files inside a workflow for newly created files. It can also be ran as a one-off job for existing files.

Checklist

If not applicable, provide explanation of why.

  • Docs updated
  • Issue linked in Title

@paulfouquet paulfouquet requested review from a team as code owners September 12, 2023 02:44
@paulfouquet paulfouquet marked this pull request as draft September 12, 2023 02:45
@paulfouquet paulfouquet marked this pull request as ready for review September 20, 2023 04:01
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
name: tpl-at-format
Copy link
Contributor

@l0b0 l0b0 Nov 2, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's "at" in this? "Argo task"? Would including "stac" somewhere be clearer, such as "tpl-at-format-stac"?

Also, other templates have names like "create-collection". Is "tpl-at-" redundant?

- name: source
description: Path to format files from
- name: target
description: (Optional) Target directory (testing)
Copy link
Contributor

@l0b0 l0b0 Nov 2, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is empty, does it format files in-place? As a newbie, that might be useful clarification. If we are relying on third party functionality, it might be OK to just link to the (appropriate version of the) reference somewhere.

default: ""
- name: fix-content-type
description: (Optional) Set the content-type to S3 object
default: ""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are valid values here? Are these MIME types, as used by the HTTP Content-Type header? What happens if this is empty?

@paulfouquet paulfouquet marked this pull request as draft December 10, 2024 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants