List gitlab projects using API - gitlab-api

I'm trying to get list of gitlab projects I've been invited to.
Using https://gitlab.com/api/v4/users/:user_id/projects I can get only list of projects I've created. But how can I get projects that I'm as a member but that I didn't create?
using endpoint https://gitlab.com/api/v4/projects with membership parameter didn't help.

Related

Combine logs from multiple systems into a single user friendly view

I have several Symfony projects generating logs. I want to be able to view these logs in a single place. This is my plan…
Each system writes logs to separate folder in an AWS s3 bucket
A Laravel project will then access these logs probably by pulling
them down to local store. Using Arcanedev Logviewer I will then view
the currently available logs.
Has anyone been able to write Symfony logs directly to an AWS s3 bucket (I've only found reference to uploading them using a cron schedule)?
As an aside, has anyone come across a web based log service that allows you to simply view logs in a format as good as Arcanedev Logviewer. We currently use Cloudwatch which is good for what it does and certainly has its place but for me the killer feature of Arcanedev Logviewer is this screen…
Arcanedev Logviewer screenshot
Thank you
Gary

How to use AWS profile with Amplify?

Amplify does not support CLI option --profile. It always uses profile specified when application was generated. Different team members use different AWS profiles.
How to change/configure/use profile different than profile used during application generation?
Aim is to publish changes from different computer. Final goal is to use CI server to publish application to different regions.
Amplify does not work like "other" development tools where tool is detached from git. Amplify goes hand in hand with Git and requires initialization after cloning. Running amplify init and choosing existing environment (which is pushed by other developer), it is possible to select different AWS profile.

Can't find AWS lambda functions deployed by Amazon Lambda Tools for .NET in AWS Lambda functions list

I'm new to AWS and I am trying to develop my first lambda function with Visual Studio code.
I have created my Hello world Lambda function using Amazon Lambda Tools for .NET Core applications (4.3.0):
dotnet new lambda.EmptyFunction helloworldcsharp.
After that i deployed it to my AWS account using
dotnet lambda deploy-function helloworldcsharp
I got and success result and when i list my functions from the CLI I get the function listed back to me.
Going to the AWS web console on the other hand I can't see the lambda function listed among the others I created online.
AWS Lambda Console functions
I thought I could be using a wrong profile but that is not the case since I see the roles I have in my account when I am deploying the function.
How can I "add" or list the functions created through Amazon lambda Tools for .NET in my account?
Am I doing something wrong and deploying it locally, somehow?
Make sure first in which region you have deployed your function (region is in your profile). And then select the same region at the top right corner in the AWS console.
Lambda is displayed per region.

Can you give blanket public access to users in a Firebase project?

I have an open-source project that uses two separate Firebase projects for a test environment and the production one.
Ultimately, I want to have other developers be able to pull down the project and actually be able to run it WITHOUT me needing to give each individual developer access.
I see a number of solutions in this question: How to add collaborators to a Firebase app?. Those all seem to require each person's email.
I understand why it maybe isn't a thing, but I am wondering if there is a way to just give access to everyone for only the test project so that contributing is super low-friction. Something similar to Firestore database rules that allow read/write in a public fashion to get started for testing.
I've tried making a new IAM account in the Google Cloud Console, and I think that partially worked for the Firebase Cloud Functions access to Admin SDK, but my collaborators get hung up trying to run firebase use <test-firebase-project> saying that they don't have access.
I see a lot of other config options for IAM, but nothing sticking out to me for this public access scenario.
Can anyone confirm this either is or isn't a thing?
Thanks!
EDIT
To add some more detail to my project...
I am using Authentication, Firestore, and Cloud Functions. The only js package I will use is the Auth one, which will be loaded from a CDN (so I believe that doesn't apply to my question).
I want to give access to people to run the Cloud Functions locally. There is a pre-build step that I have made in vanilla Node that calls a Cloud Function (running locally), which uses the Firebase Admin SDK to call my Firestore database. I then write that response to a JSON file that my front end uses.
When my collaborators pull down the project, and install the Firebase CLI, when they try to serve the Cloud Functions locally, they get hit with a "no access" type of error. I was trying to resolve this by adding a service account into the /functions directory, but apparently that didn't help.
My collaborators don't need access to the console at all. I basically just need them to be able to run the Cloud Function locally (and make sure they can't access my production Firebase project).
I am happy to add more detail, but I kind of feel like I am just rambling. Thanks again.
There is no way to grant everyone contributor access to your Firebase console. You will either have add each individual user, or create your own dashboard that uses the API to show the relevant data.

403 when using firebase API to create a project (As an owner user, not a service account)

I am trying to create a firebase project using the api. The document for this is here: https://firebase.google.com/docs/projects/api/reference/rest/v1beta1/projects/addFirebase
I have created a GCP project already and I am the owner of this project. I can see my project in a request to:
https://firebase.google.com/docs/projects/api/reference/rest/v1beta1/availableProjects/list . It has a project id of: projects/my-project-id-here
I am making the requests as a owner of the GCP project user account (I am not using a service account!) using Google OAuth 2.0 with the correct scopes (You can try it in the documentation), but I am receiving a response of:
{
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}
I can create firebase project fine If I go to firebase website directly and create the project there.
Google take 30 days to delete my test projects, so I am restricted to how many times I can try to get this right from scratch. Therefore I am also interested to know how you fully unlink firebase from a GCP project without deleting that project. Removing the service account and disabling the APIs from GCP console doesn't seem to do the trick.
Finally, I do not know if it is relevant but I also have the same user account setup with a developer account on google play and the GCP project is linked up for API access it's created service account granted access. I don't think this is relevant though, as my understanding is that I can setup a firebase project without this.
Hope someone can help!
I've found the solution to this. You cannot use the firebase API to create a firebase project unless you've first accepted the terms and conditions which aren't shown to you until you're in a firebase project (go figure).
Anyway here are some clear steps:
Create a firebase project through the website
Open the firebase project
Accept the terms and conditions for firebase use
Delete the firebase project and enjoy the API now working.
Regarding your interest in removing firebase from a project, this is not supported. The best course of action is to undo the changes that were made when firebase was added, namely disabling the firebase APIs, removing oauth client/brand, removing API keys etc, which you have already done, and it’s the closest thing to deleting the project.

Resources