orchestration | SODA Orchestration project is an open source workflow | Job Orchestrator library

I am trying to get the cloud composer proxy url to trigger dags from cloud function. I am following below blog. however it's failing while retrieving this url.

https://medium.com/google-cloud/calling-cloud-composer-to-cloud-functions-and-back-again-securely-8e65d783acce

Command

I have some long saltstack orchestration states and i want to add some informational messages to it (for example: Gonna apply some state on minion foo) ,and this messages must be printed immediately ( not after all actions completed).

Jinja log message {% do salt.log.error("Some message) %} is not suitable (they printed before state actually runs).

test.echo module also not suitable (prints message after all actions completed)

I am facing the following problem: I need to execute on-demand long running workers on Azure VMs. These workers are wrapped in a docker image.

So I looked at what Azure is offering and I seem to have the following two options:

1. Use a VM with docker-compose. This means I need to be able to programatically start a VM, run the docker image on it, and then shutdown the VM (the specs we use are quite expensive and we can't let it run indefinitely). However this means writing orchestration logic ourselves. Is there a service that maybe we could use to make life easier?

2. Setting up a k8s cluster. However, I am not sure how pricing works here. Would I be able to add the type of the VMs we use to the cluster, and then use the k8s API to start on-demand containers? How would I get priced in this case?

I'm really inexperienced with this. I'm a programmer, not a sysadmin. I'm trying to run a windows docker container on a windows host using this command:

I am currently working on one project where it requires the custom authentication process. This application will be deployed on AWS platform, in which I am considering to use below AWS services like

1. API Gateway
2. Custom Authorization
3. EKS

The plan is to deploy all backend services in the docker containers and use EKS service for container orchestration process. All input request will be validated through API gateway and routed to the respective backend services.
We are going to use custom authorization process with below possible steps:

1. Our application (say CHILD-APP) will be integrated with an existing application (say PARENT-APP), where the PARENT-APP will take care of the user authentication.
2. On successful user authentication, the PARENT-APP will request the access token (JWT Token) to CHILD-APP.
3. This access token will be used by CHILD-APP User Interface to make the backend request calls.
4. We are using custom access token validation process to check the token integrity, the username validation and other additional validations (cannot be exposed due to compliances).
5. Currently I am using the Spring Boot API Gateway for URL routings, and for access token validations.
6. Also using custom Spring Cloud Eureka server to register the services.

Questions:

1. How to use the AWS API Gateway for such custom authentication and authorization process?
2. Can I use the Spring Cloud Eureka server and custom authorization along with the AWS API Gateway?

Any help related to this is appreciated.

Thanks,

Avinash

Both replica set and deployment have the attribute replica: 3, what's the difference between deployment and replica set? Does deployment work via replica set under the hood?

configuration of deployment

We are using the following command to deploy BizTalk assemblies via PowerShell:

I've setup a BizTalk design that chains a couple of send/receives to a SQL stored procedure (which inserts the data to relevant tables). It's organised in a specific sequence, so data goes into Table A, and following tables after this check that the data exists in Table A at the Stored Procedure level (simple (IF EXISTS in Table A setup...).

I've noticed though that the flow isn't consistent further down the chain, almost as if SQL is executing the stored procedure to insert/update the record slower than the BizTalk transaction is occurring. I've made sure that my Biz design is send/receive, as I assumed the transaction wouldn't progress until Biz received a response from the stored procedure (which would indicate SQL has finished inserting the required data).

The below example highlights where the process writes data to the Person table, but is later called upon by the Student Programme/Student Module. Occasionally, it will dehydrate on the Programme or Module stored procedure (from what I can tell, because the stored procedures are looking to see if a Person record created at the start of the flow exists)

Can anyone please confirm if;

• Send/Receive will wait for a SQL stored procedure to finish executing before progressing the BizTalk transaction further through the orchestration?

Building a step function to orchestrate an ETL pipeline but keep getting this error. Here is my code and following below AWS docs. https://docs.aws.amazon.com/step-functions/latest/dg/sample-etl-orchestration.html