cd | A better cd '' for bash | File Utils library

We are experimenting with Jetbrains Space as our code repo and CI/CD. We are trying to find a way to setup the .space.kts file to deploy to AWS Lambda.

We want the develop branch to publish to the Lambda $Latest and when we merge to the main branch from the develop branch we want it to publish a new Lambda version and link that version to the alias pro.

I've looked around but haven't found anything that would suggest there is a pre-built solution for controlling AWS Lambda so my current thinking is something like this:

I have written the following class in Typescript:

I need to use Python3.7, so I followed these instructions to install it

I'm starting to use gitlab CI/CD pipeline but have some doubts regarding the output of the building process if i was to have a project(Repo) and inside this project I have the front and backend separated by the project structure, ex:

.gitlab-ci.yml

|__FrontEndCarProject

|__BackendCarProject

let's say that every time I change something in the frontend I would need to build it and deploy it to S3, but there is no need to build the backend (java application) and deploy it to elastic beanstalk (and vice versa for when i change the backend)..Is there a way to check where the changes have been made(FrontEndCarProject/BackendCarProject) using GitLab and redirect the .gitlab-ci.yml to a script file depending on if a have to deploy to S3 or elastic beanstalk?

Just trying

Note: another way is just to manually change the yml file depending on where i want to deploy..but is there a way to autodetect this and automated?

Just to get the idea, heres an example that would run in a linear way, but how can i conditionally build/deploy(depending on my front or backend)? should i keep them in different repos for simplicity? is it a good practice?

I am able to do most things inside the dir, but I can't cd out of it, trying /bin/sh causes the shell to freeze.

I'm running gitlab-ce on-prem with min.io as a local S3 service. CI/CD caching is working, and basic connectivity with the S3-compatible minio is good. (Versions: gitlab-ce:13.9.2-ce.0, gitlab-runner:v13.9.0, and minio/minio:latest currently c253244b6fb0.)

Is there additional configuration to differentiate between job-artifacts and pipeline-artifacts and storing them in on-prem S3-compatible object storage?

In my test repo, the "build" stage builds a sparse R package. When I was using local in-gitlab job artifacts, it succeeds and moves on to the "test" and "deploy" stages, no problems. (And that works with S3-stored cache, though that configuration is solely within gitlab-runner.) Now that I've configured minio as a local S3-compatible object storage for artifacts, though, it fails.

Whenever I run this program, it completes the first function perfectly and then ends the program before doing anything else. How can I allow the other two functions to run?

I have two tables. Table A - Base table with full data. Table B - Contains grouped data by the combination (Origin- Destination- Carrier- Class). It has only those combinations which have both Premium and Economy class and also greater than 100 passengers each.

My objective is to only include those rows in Table A which pertain to combinations in Table B. Sample tables are below -

Table A

Table B

The output table that I need is-

Also, is there a way to skip making Table B altogether and directly running operation on Table A to get the output table?

Thank you

I have a directory that contains txt files with unique times that gets generated overnight. I am trying to list those files given the unique timestamps in the file. Some example of file names are the following: