Error:
An error occurred while fetching the app backend: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
.aws/config:
[profile projectname]
output=json
region=ca-central-1
[profile projectname-dev]
region=ca-central-1
source_profile=projectname
role_arn=arn:aws:iam::*******:role/projectname-dev-admin
[profile projectname-qa]
region=ca-central-1
source_profile=projectname
role_arn=arn:aws:iam::******:role/projectname-qa-admin
[profile projectname-prod]
region=ca-central-1
source_profile=projectname
role_arn=arn:aws:iam::*******:role/projectname-prod-admin
.aws/credentials
[projectname]
aws_access_key_id=********
aws_secret_access_key=*******
using aws-vault to swap between profiles and have been working this way for the last 8 months without issue until this morning when i went to push a change.
Any ideas would be much appreciated!
Related
I'm trying to call Access package assignment approval update via MSGraph Beta API (Java 0.51.0-SNAPSHOT). The call fails with following error:
2022-08-26 22:32:44.239 ERROR 10208 --- [nio-9999-exec-4] global : CoreHttpProvider[sendRequestInternal] - 408Graph service exception
2022-08-26 22:32:44.239 ERROR 10208 --- [nio-9999-exec-4] global : Throwable detail: com.microsoft.graph.http.GraphServiceException: Error code:
Error message: Only user tokens are supported
PATCH https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentApprovals/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa/steps/bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb
SdkVersion : graph-java/v0.51.0
[...]
403 : Forbidden
[...]
[Some information was truncated for brevity, enable debug logging for more details]
Based on the error message can I think, that Application tokens are not really supported, but the strange thing is, that I can call Access package assignment approval get without any issue. I have of course delegated the permission EntitlementManagement.ReadWrite.All to the Application user.
I tried to reproduce the same in my environment using Graph Explorer and got the below results:
I am able to retrieve the properties of an approval object successfully like this:
GET https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentApprovals/<id>
Response:
To update those properties, I ran the same query as you like below, and it got updated successfully:
PATCH https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentApprovals/<id>/steps/<id>
{
"reviewResult": "Approve",
"justification": "Please approve"
}
Response:
Make sure to pass 'Request body' with the PATCH query. Please check whether you are giving correct id's or not in the query.
The <id> before /steps/ in the query is the id of accessPackageAssignmentRequest that is in PendingApproval State.
To get that id, you can run the below query:
GET https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentRequests?$expand=requestor($expand=connectedOrganization)&$filter=(requestState eq 'PendingApproval')
Response:
The <id> after /steps/ in the query is the step id that I got by running below query:
GET https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentApprovals/<id_that_you _got_in_above_query>
Response:
UPDATE
Please note that, you cannot update Access package assignment approval using Application permissions. Application permissions are not supported for PATCH query.
You can refer this MsDoc to confirm that like below:
So, it will only work if you login with work or school account(personal-login)
based on aws documetation (https://docs.aws.amazon.com/sagemaker/latest/dg/serverless-endpoints-create.html) ,
response = client.create_endpoint_config(
EndpointConfigName="<your-endpoint-configuration>",
ProductionVariants=[
{
"ModelName": "<your-model-name>",
"VariantName": "AllTraffic",
"ServerlessConfig": {
"MemorySizeInMB": 2048,
"MaxConcurrency": 20
}
}
]
)
i created an serverless endpoint (sample code above) , but I keep getting error when the endpoint is invoked , has anyone run into this issue - 'Error - / .sagemaker/ts/models/model.mar already exists. Please specify --force/-f option to overwrite the model archive output file' . FYI - this worked when the endpoint was configured provisioned instead of serverless.
You can checkout a few examples we created here
Tried to deploy to Heroku - Failed! Went back to commit prior to attempting Heroku deployment. Now posting form doesn't work and the log is stating that a parameter which is whitelisted isn't permitted?
Not sure what's happened! Post form was working
http://imgur.com/W6FxL7n
posts_controller.rb
private
def post_params
params.require(:post).permit(:tag_list, :id, things_attributes: [:text, :url, :order, :image, :quote, :source, :video, :id])
end
You are whitelisting things_attributes, but your form is submitting some stuff under things_attributes and other stuff under thing_attributes (singular not plural). So fix your form so that everything is things_attributes and you should be fine.
I've only started to have this problem having upgraded all of my libraries:
I was using GWT 2.4, App Engine 1.6.3 and Objectify 3.0.
I upgraded to GWT 2.5, App Engine 1.7.4 and Objectify 4.0b1.
Since then I am getting this strange error that only 1 other person seems to have on the entire internet!
Stack trace:
Caused by: com.google.gwt.user.client.rpc.SerializationException: com.google.appengine.api.datastore.Key/1349195865
at com.google.gwt.user.client.rpc.impl.SerializerBase.getTypeHandler(SerializerBase.java:153)
at com.google.gwt.user.client.rpc.impl.SerializerBase.instantiate(SerializerBase.java:114)
at com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(ClientSerializationStreamReader.java:396)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:119)
at com.googlecode.objectify.Key_FieldSerializer.deserialize(Key_FieldSerializer.java:11)
at com.googlecode.objectify.Key_FieldSerializer.deserial(Key_FieldSerializer.java:29)
at com.google.gwt.user.client.rpc.impl.SerializerBase.deserialize(SerializerBase.java:95)
at com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(ClientSerializationStreamReader.java:398)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:119)
at com.google.gwt.user.client.rpc.core.java.util.Collection_CustomFieldSerializerBase.deserialize(Collection_CustomFieldSerializerBase.java:34)
at com.google.gwt.user.client.rpc.core.java.util.ArrayList_CustomFieldSerializer.deserialize(ArrayList_CustomFieldSerializer.java:34)
at com.google.gwt.user.client.rpc.core.java.util.ArrayList_FieldSerializer.deserial(ArrayList_FieldSerializer.java:19)
at com.google.gwt.user.client.rpc.impl.SerializerBase.deserialize(SerializerBase.java:95)
at com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(ClientSerializationStreamReader.java:398)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:119)
at com.utilitiessavings.testapp2.shared.Account_FieldSerializer.deserialize(Account_FieldSerializer.java:29)
at com.utilitiessavings.testapp2.shared.Account_FieldSerializer.deserial(Account_FieldSerializer.java:51)
at com.google.gwt.user.client.rpc.impl.SerializerBase.deserialize(SerializerBase.java:95)
at com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(ClientSerializationStreamReader.java:398)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:119)
at com.google.gwt.user.client.rpc.core.java.util.Collection_CustomFieldSerializerBase.deserialize(Collection_CustomFieldSerializerBase.java:34)
at com.google.gwt.user.client.rpc.core.java.util.ArrayList_CustomFieldSerializer.deserialize(ArrayList_CustomFieldSerializer.java:34)
at com.google.gwt.user.client.rpc.core.java.util.ArrayList_FieldSerializer.deserial(ArrayList_FieldSerializer.java:19)
at com.google.gwt.user.client.rpc.impl.SerializerBase.deserialize(SerializerBase.java:95)
at com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(ClientSerializationStreamReader.java:398)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:119)
at com.utilitiessavings.testapp2.client.action.GetAccountsResult_FieldSerializer.deserialize(GetAccountsResult_FieldSerializer.java:20)
at com.utilitiessavings.testapp2.client.action.GetAccountsResult_FieldSerializer.deserial(GetAccountsResult_FieldSerializer.java:38)
at com.google.gwt.user.client.rpc.impl.SerializerBase.deserialize(SerializerBase.java:95)
at com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize(ClientSerializationStreamReader.java:398)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:119)
at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter$ResponseReader$8.read(RequestCallbackAdapter.java:106)
at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:214)
... 27 more
The problem is occuring when deserializing Account as it contains an Objectify Key which wraps the native datastore key.
Serializing works fine, and my object graph is all fine and dandy in the datastore, I just can't get anything back that contains a Key, which is pretty much everything useful.
Any pointers appreciated.
I've had this same issue and it seems that it has nothing to do with the datastore either because when I sent an object to the server and tried to retrieve it back I still got a deserialization error.
AsyncCallService{
void createUser(User user, AsyncCallback<User> user);
}
ServiceImpl{
User createUser(User user){
DB.save(user);
return user
}
And this is still causing Serialization errors or rather deserializaton errors on the client.
What I've done was just pass back a new User;
User createUser(User user){
DB.save(user);
User newUser = new User();
newUser.setId(user.getId())
return newUser;
}
Problem solved except that now I've lost some of the "benefits" of older app engine stack where deserialization wasn't necessary.
I tried to run a GAE project and when I was using command : dev_appserver.py, I got this error message(complete one)
:
WARNING 2011-07-26 04:25:29,342 urlfetch_stub.py:108] No ssl package found. url
fetch will not be able to validate SSL certificates.
INFO 2011-07-26 04:25:29,515 appengine_rpc.py:159] Server: appengine.google.
com
INFO 2011-07-26 04:25:29,530 appcfg.py:456] Checking for updates to the SDK.
INFO 2011-07-26 04:25:33,875 appcfg.py:473] The SDK is up to date.
WARNING 2011-07-26 04:25:33,890 datastore_file_stub.py:511] Could not read data
store data from d:\360data\重要数据\用户临~1\dev_appserver.datastore
INFO 2011-07-26 04:25:33,890 rdbms_sqlite.py:58] Connecting to SQLite databa
se '' with file 'd:\\360data\\\xd6\xd8\xd2\xaa\xca\xfd\xbe\xdd\\\xd3\xc3\xbb\xa7
\xc1\xd9~1\\dev_appserver.rdbms'
ERROR 2011-07-26 04:25:33,890 dev_appserver_main.py:638] <class 'sqlite3.Oper
ationalError'>: unable to open database file
I searched for the solution, and I got sample answers like "including Unicode and can't get my user name or use the launcher with admin flag or delete the 'dev_appserver.rdbms' file" , but I'm not clear with that(what exactly to do), how to solve this problem, I can't get the file 'dev_appserver.rdbms', because the path "'d:\360data\\xd6\xd8\xd2\xaa\xca\xfd\xbe\xdd\\xd3\xc3\xbb\xa7\xc1\xd9~1\" does not exist after "d:\360data\", this prob taunts me and I can't go on , hope I can get a clear guidance from you :>