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.

Sign up for GitHub

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

Jump to bottom

create pipectl init command #4677

Open
3 of 10 tasks
ffjlabo opened this issue Nov 17, 2023 · 5 comments
Open
3 of 10 tasks

create pipectl init command #4677

ffjlabo opened this issue Nov 17, 2023 · 5 comments
Labels
area/pipectl epic

Comments

@ffjlabo
Copy link
Member

ffjlabo commented Nov 17, 2023 •
edited by t-kikuc
Loading

What would you like to be added:
#4635

  • Kubernetes QuickSync
  • Kubernetes Pipeline Sync
  • ECS QuickSync
  • ECS Pipeline Sync
  • Lambda QuickSync
  • Lambda Pipeline Sync
  • Terraform QuickSync
  • Terraform Pipeline Sync
  • CloudRun QuickSync
  • CloudRun Pipeline Sync

Why is this needed:
@ffjlabo ffjlabo added this to v0.46.0 Nov 17, 2023
@ffjlabo ffjlabo moved this to Todo in v0.46.0 Nov 17, 2023
@ffjlabo ffjlabo moved this from Todo to In Progress in v0.46.0 Dec 22, 2023
@t-kikuc t-kikuc mentioned this issue Dec 26, 2023
Merged
@ffjlabo
Copy link
Member Author

ffjlabo commented Jan 19, 2024

@t-kikuc
This is an epic issue.
Let's split issue by platform like

  • ECS
  • k8s
  • Terraform...

@ffjlabo ffjlabo added the epic label Jan 19, 2024
@t-kikuc t-kikuc mentioned this issue Jan 19, 2024
Closed
@t-kikuc
Copy link
Member

t-kikuc commented Jan 19, 2024 •
edited
Loading

Support status of simplest patterns (ToDo)

higher priority

  • Kubernetes
    • QuickSync
    • Pipeline Sync
  • ECS
    • QuickSync (service with one ELB target group)
    • Pipeline Sync

later

  • Terraform
    • QuickSync
    • Pipeline Sync
  • Lambda
    • QuickSync
    • Pipeline Sync
  • CloudRun
    • QuickSync
    • Pipeline Sync

@t-kikuc t-kikuc removed this from v0.46.0 Jan 19, 2024
@t-kikuc
Copy link
Member

t-kikuc commented Jan 31, 2024

💡 A great idea from kentakozuka:

How about configuring the analysis stage (without any restriction) for canary&blue/green pipeline?

The effects:

  • Force users to follow best practices
  • Users can easily recognize features

@ffjlabo
Copy link
Member Author

ffjlabo commented Jan 31, 2024

It sounds good 👍 Nice idea! I agree with it.

@t-kikuc t-kikuc mentioned this issue Mar 1, 2024
Closed
@t-kikuc t-kikuc removed their assignment Mar 7, 2024
@t-kikuc
Copy link
Member

t-kikuc commented Dec 3, 2024

I think we should probably deprecate the current init command since the config will depend on each plugin...

And the current init only supports pipedv0's config, which won't be used after the plugin architecture is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/pipectl epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ffjlabo @t-kikuc